Origin: upstream, https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1824.patch
Applied-Upstream: 25.06.0, https://gitlab.freedesktop.org/poppler/poppler/-/commit/55169105e121d5fbb7c50e2c744d750de5d0a7de
Bug: https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1596
Bug-Debian: https://bugs.debian.org/1127146 Reviewed-By: John Scott <jscott@posteo.net>
Last-Update: 2026-07-01
strftime places a NULL-terminated string in the buffer, so the std::string
buffer needs to be resized to not include the terminator character
(or anything after it).
Without this fix, modification dates in altered PDF documents (such as when
adding a digital signature) are not truncated properly, instead padding
the date with a null byte and extra spaces until the end of the buffer is
reached. This bad syntax compromises the ability to verify the signature
with other applications, but the Poppler signatory has no indication of this.
Juraj Šarinay [Thu, 6 Mar 2025 01:02:56 +0000 (02:02 +0100)]
Properly verify adbe.pkcs7.sha1 signatures.
For signatures with non-empty encapsulated content
(typically adbe.pkcs7.sha1), we only compared hash values and
never actually checked SignatureValue within SignerInfo.
The bug introduced by c7c0207b1cfe49a4353d6cda93dbebef4508138f
made trivial signature forgeries possible. Fix this by calling
NSS_CMSSignerInfo_Verify() after the hash values compare equal.
* Team upload
* Fix creation of ill-formed PDF document signatures (Poppler issue #1596)
- fixes "Invalid signature time when signing a PDF" (Closes: #1127146)
Signatures made with previous versions of Poppler may not be recognized
by other applications as valid.
Juraj Šarinay [Thu, 6 Mar 2025 01:02:56 +0000 (02:02 +0100)]
Properly verify adbe.pkcs7.sha1 signatures.
For signatures with non-empty encapsulated content
(typically adbe.pkcs7.sha1), we only compared hash values and
never actually checked SignatureValue within SignerInfo.
The bug introduced by c7c0207b1cfe49a4353d6cda93dbebef4508138f
made trivial signature forgeries possible. Fix this by calling
NSS_CMSSignerInfo_Verify() after the hash values compare equal.
* Non-maintainer upload by the Security Team.
* SplashOutputDev: Fix integer overflow in tilingPatternFill (CVE-2026-10118)
(Closes: #1138708)
* Make sure regex doesn't stack overflow by limiting it (CVE-2025-43718)
(Closes: #1117046)
* Check for duplicate entries (CVE-2025-52885) (Closes: #1117853)
Juraj Šarinay [Thu, 6 Mar 2025 01:02:56 +0000 (02:02 +0100)]
Properly verify adbe.pkcs7.sha1 signatures.
For signatures with non-empty encapsulated content
(typically adbe.pkcs7.sha1), we only compared hash values and
never actually checked SignatureValue within SignerInfo.
The bug introduced by c7c0207b1cfe49a4353d6cda93dbebef4508138f
made trivial signature forgeries possible. Fix this by calling
NSS_CMSSignerInfo_Verify() after the hash values compare equal.
Jeremy Bícha [Sun, 31 Aug 2025 18:01:36 +0000 (14:01 -0400)]
poppler (25.03.0-5+deb13u2) trixie; urgency=high
[ Leonidas Da Silva Barbosa ]
* SECURITY UPDATE: Denial of service
- debian/patches/CVE-2025-50420.patch: don't continue
recursing in PDFDoc in poppler/PDFDoc.cc.
- CVE-2025-50420 (Closes: #1110463)
Juraj Šarinay [Thu, 6 Mar 2025 01:02:56 +0000 (02:02 +0100)]
Properly verify adbe.pkcs7.sha1 signatures.
For signatures with non-empty encapsulated content
(typically adbe.pkcs7.sha1), we only compared hash values and
never actually checked SignatureValue within SignerInfo.
The bug introduced by c7c0207b1cfe49a4353d6cda93dbebef4508138f
made trivial signature forgeries possible. Fix this by calling
NSS_CMSSignerInfo_Verify() after the hash values compare equal.
Jeremy Bícha [Mon, 28 Jul 2025 08:55:12 +0000 (10:55 +0200)]
poppler (25.03.0-5) unstable; urgency=high
[ Marc Deslauriers ]
* SECURITY UPDATE: DoS via reference count overflow
- debian/patches/CVE-2025-52886.patch: limit amount of annots per
document/page in poppler/Annot.cc, poppler/Page.cc.
- CVE-2025-52886 (Closes: #1108784)
Juraj Šarinay [Thu, 6 Mar 2025 01:02:56 +0000 (02:02 +0100)]
Properly verify adbe.pkcs7.sha1 signatures.
For signatures with non-empty encapsulated content
(typically adbe.pkcs7.sha1), we only compared hash values and
never actually checked SignatureValue within SignerInfo.
The bug introduced by c7c0207b1cfe49a4353d6cda93dbebef4508138f
made trivial signature forgeries possible. Fix this by calling
NSS_CMSSignerInfo_Verify() after the hash values compare equal.
Jeremy Bícha [Fri, 18 Apr 2025 22:16:32 +0000 (18:16 -0400)]
poppler (25.03.0-4) unstable; urgency=high
* Team upload
* SECURITY UPDATE: Properly verify abde.pkcs7.sha1 signatures
- Cherry-pick upstream fix for the
NSSSignatureVerification::validateSignature function
in NSSCryptoSignBackend.cc
- CVE-2025-43903 (Closes: #1103545)